Received: from relay5.UU.NET (relay5.UU.NET [192.48.96.15]) by keeper.albany.net (8.7.1/8.7.1) with ESMTP id OAA04196 for <dwarner@albany.net>; Sun, 10 Dec 1995 14:49:44 -0500 (EST)
Received: from garcia.com by relay5.UU.NET with SMTP
id QQztnz19059; Sun, 10 Dec 1995 14:45:21 -0500 (EST)
Received: from (localhost) by garcia.com (5.x/SMI-SVR4)
id AA10687; Sun, 10 Dec 1995 14:45:46 -0500
Date: Sun, 10 Dec 1995 14:45:46 -0500
Errors-To: dwarner@albany.net
Message-Id: <199512101939.MAA28216@earth.usa.net>
Errors-To: dwarner@albany.net
Reply-To: lightwave@garcia.com
Originator: lightwave@garcia.com
Sender: lightwave@garcia.com
Precedence: bulk
From: James Jones/Nibbles and Bits <jgjones@usa.net>
To: Multiple recipients of list <lightwave@garcia.com>
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Status: RO
X-Status:
Subject: Subject:
Subject: This is a subject line.
This line thinks it's a subject line, but really isn't.
Subject: This IS a subject line, but to its own utter
consternation, lacks one completely.
Subject: This subject line, frustrated out of its gourd by not being
included in the message header where it belongs, will
attempt to explain that the internet provider that sent
this EMail message whacks all QWK-Mail subject lines that
pass through its bowels.
Subject: This subject line, growing tired of the whole discussion,
apologizes for the veiled reference to shit in the previous
subject line, and decides to quit this nonsense and get on
with the message.
Subject: But fails, miserably.
Subject: This subject line, however, succeeds.
Jdavid@infinet.com said:
>>Subject: LHAing on NT
>>
>
>This is showing up within the message, not the Subject Field...